System and method for managing communication links

ABSTRACT

A system and method for managing a communication link between a consumer electronic device adapted for two-way, wireless communications with at least one peripheral. The communication link is managed using a controller that is associated with the consumer electronic device that functions to assign communication slots to the peripheral to facilitate communications between the peripheral and the consumer electronic device.

RELATED APPLICATIONS

This application claims the benefit of and is a continuation of U.S.application Ser. No. 13/922,655, filed on Jun. 20, 2013, whichapplication claims the benefit of and is a continuation of U.S.application Ser. No. 11/502,780, filed on Aug. 11, 2006, whichapplication claims the benefit of and is a divisional of U.S.application Ser. No. 10/431,930, filed on May 8, 2003, which applicationclaims the benefit of U.S. Provisional Application No. 60/386,301, filedon Jun. 5, 2002, the disclosures of which are incorporated herein byreference in their entirety.

BACKGROUND

The following relates generally to communication links and, moreparticularly, relates to a system and method for managing communicationlinks using a bi-directional communication protocol.

Bi-directional communication protocols are known in the art. Forexample, U.S. Pat. No. 5,564,020 described two units, one of which isinstalled in a computer and one of which is located remotely withrespect to the computer, that communicate over an infrared (IR) link.Each unit has a serial number to identify itself and to keep acommunication link secure once established. The IR link is establishedby hitting an initialization switch on each of the two units, at whichtime they commence transmitting their serial numbers and anacknowledgement process occurs. Once this initialization has occurredand both units have registered with the other unit, only communicationsfrom the proper serial number provider are accepted. After theinitialization phase, data and commands are sent between the two unitsin a packetized structure which allows error checking as necessary.

By way of further example, U.S. Pat. No. 5,917,631 describes using apulse position modulation (PPM) scheme, similar to that described byGarrett in U.S. Pat. No. 4,584,720, to establish a communication linkbetween a remote control and a receiving unit. This PPM scheme uses theposition of a single pulse, such as an IR pulse, to indicate a multi-bitvalue. For example, a sixteen or greater position PPM scheme may be usedto encode four-bit hexadecimal data values. In this way, the singlepulse may substitute for what otherwise would have been multiple pulsesin a simple binary encoding scheme.

By way of still further example, U.S. Pat. No. 5,640,160 describes a PPMmodulation protocol where a binary code is divided into 2-bit data unitsand pulse position modulation is performed on each unit rather than oneach bit. In this manner, since a pulse is not formed for each bit, thetransmission interval and transmission frame interval for the modulatedsignal is shortened, thus enabling high speed transmission. In addition,since the width of the pulse does not contain any transmissioninformation, the pulse width is made as short as possible, therebyreducing battery consumption within the transmitter.

While such bi-directional communication protocols do work for theirintended purpose, what is needed is an improved system and method formanaging bi-directional communication links.

SUMMARY

In accordance with this need, a system and method is described wherein aconsumer electronic device is adapted for two-way, wirelesscommunications with at least one peripheral device. The consumerelectronic device is further associated with a controller that functionsto assign communication slots to the peripheral to facilitatecommunications between the peripheral and the consumer electronicdevice. Communications may be performed using a bi-directional IRprotocol such as, for example, TWIRP 32X which transmits data using PPMmodulation and a sub-carrier of 455 kHz.

A better understanding of the objects, advantages, features, propertiesand relationships of the subject system and method will be obtained fromthe following detailed description and accompanying drawings which setforth illustrative embodiments which are indicative of the various waysin which the principles of the system and method may be employed.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the system and method for managingcommunication links, reference may be had to preferred embodiments shownin the following drawings in which:

FIG. 1 illustrates, in flowchart form, an example of the overall logicflow followed by a peripheral in the acquisition of a time slot from aTS Controller and transfer of data using the registered slot;

FIG. 2 illustrates, in graphical form, the sequential exchange of datapackets between the TS Controller and a single peripheral transferring asingle packet of data;

FIG. 3 illustrates, in graphical form, the sequential exchange of datapackets between the TS Controller and a single peripheral transferringmultiple packets of data;

FIG. 4 illustrates, in graphical form, the sequential exchange of datapackets between the TS Controller and multiple devices registering andperforming simultaneous (interleaved) data transfer;

FIG. 5 illustrates an exemplary “Outbound Link Management” packetwherein fields that are associated with other protocol layers such aserror detection, etc., and that are not involved in link management areomitted for the sake of clarity (e.g., indicated by a “X” protocol bit);

FIG. 6 illustrates an exemplary “End-of-Cycle” link management packetwherein fields that are associated with other protocol layers such aserror detection, etc., and that are not involved in link management areomitted for the sake of clarity (e.g., indicated by a “X” protocol bit);

FIG. 7 illustrates an exemplary “General Long Packet” format whereinfields that are associated with other protocol layers such as errordetection, etc., and that are not involved in link management areomitted for the sake of clarity (e.g., indicated by a “X” protocol bit);

FIG. 8 illustrates an exemplary “Peripheral Packet” format whereinfields that are associated with other protocol layers such as errordetection, etc., and that are not involved in link management areomitted for the sake of clarity (e.g., indicated by a “X” protocol bit);

FIG. 9 illustrates an exemplary “Peripheral Registry” packet whereinfields that are associated with other protocol layers such as errordetection, etc., and that are not involved in link management areomitted for the sake of clarity (e.g., indicated by a “X” protocol bit);

FIGS. 10A-C each illustrates an exemplary “Peripheral Data” packetwherein fields that are associated with other protocol layers such aserror detection, etc., and that are not involved in link management areomitted for the sake of clarity (e.g., indicated by a “X” protocol bit);and

FIG. 11 illustrates an exemplary “Outbound Binary Data” packet whereinfields that are associated with other protocol layers such as errordetection, etc., and that are not involved in link management areomitted for the sake of clarity (e.g., indicated by a “X” protocol bit).

DETAILED DESCRIPTION

With reference to the Figures, a system and method is described whereina master station transceiver, hereafter referred to as a Time SlotController (“TS Controller”), directs and synchronizes thecommunications of a plurality of peripherals, e.g., up to sixty-three(63), sharing a communication link. In a preferred embodiment, the TScontroller is associated with a consumer electronic device, e.g., apiece of home entertainment equipment, a game console, etc., and theperipherals comprise one or more controlling peripheral devices, e.g., aremote control, game controller, keyboard, etc., wherein the peripheralsare adapted to transmit and/or receive communications, via the TScontroller, with the consumer electronic device. As will be appreciated,the TS controller is associated with the consumer electronic device bybeing embedded within the consumer electronic device or by beingdistinct from the consumer electronic device but in furthercommunication with the consumer electronic device, either via wired orwireless transmissions. In this manner, a one to many correspondence iscreated between the TS Controller/consumer electronic equipment andperipherals by which multiple peripherals can be used to command theoperation of and/or receive feed back from a consumer electronic device.

To facilitate communication via the communication link, a given protocolcycle within the communication link may be divided into four (4)general-purpose time slots and one dedicated protocol control andsynchronization time slot. Each of these four (4) general purpose timeslots can accommodate a single inbound or outbound data packet and maybe demarcated by a marker pulse transmitted by the TS controller. Atdifferent times a given protocol cycle might be used for dynamic inboundperipheral packets, inbound or outbound binary data packets, and/orpolled inbound peripheral packets. Both long packets, e.g., forty-two(42) bits, and short packets, e.g., twenty-four (24) bits, may besupported. As described in more detail in the following sections, timeslots are dynamically assigned and contended for by multiple peripheralsunder the supervision of the TS controller utilizing the aforementioneddedicated protocol control and synchronization time slot. In thismanner, the dynamic assignment of time slots enables more peripheraldevices to be used within the system than there are time slots availablein a single protocol cycle, i.e., individual peripheral devices maysuccessively register, obtain a time slot, transfer data, and thenrelinquish the time slot for use by other peripheral devices.Alternatively, individual peripheral devices may be polled by the TScontroller in a cyclic fashion, responding in time slots indicated ineach poll request. The length of each time slot may also be dynamicallyvariable under the supervision of the TS controller such that multipledata packet sizes may be supported and empty (idle) slots occupy aminimum amount of time.

To allow for the sharing of the communication link, a slotted roundrobin scheme may be utilized. In this approach, either no packet or asingle packet may be transferred during each time slot; either inboundto, or outbound from the TS Controller. Furthermore, individual timeslots may operate in one of two modes at any given time, namely,dedicated half-duplex with any given peripheral device or sequentialautomatic polling for responses from a group of peripheral devices.Sharing of the communication link may be further facilitated byproviding individual peripherals with an assigned, unique twenty one-bit(21-bit) registry number. This registry number may serve, for example,to define capabilities and functions of a peripheral device and/oridentify to which application or driver software module within the TScontroller or appliance the data received from a peripheral device is tobe directed. The assignment of registry numbers is preferably maintainedby a central registration authority.

In order to acquire a time slot and transmit data, a peripheral monitorsthe communication link for activity as illustrated in FIG. 1. If thecommunication link is active, the peripheral examines the “Outbound LinkManagement” packet(s) transmitted by the TS controller until an“End-of-Cycle” packet is detected. The peripheral then examines the datacontent of the “End-of-Cycle” packet to find a time slot which is idleas will be described further in conjunction with FIGS. 5 and 6.

Turning to FIG. 5, there is illustrated an exemplary general format foran “Outbound Link Management” packet. The “Outbound Link Management”packet may comprise 30 bits of information, which have been arranged inFIG. 5 as five 6-bit long words for ease of reference only. Inparticular, if the two Protocol Operation Mode bits M0 and M1(illustrated in locations 1-4 and 1-5 in FIG. 5) are both zero, thepacket is an “End-of-Cycle” packet and the payload data bits D0 thru D21of FIG. 5 assume the significance illustrated in FIG. 6. Specifically,in the packet illustrated FIG. 6, the current state and availability ofeach of the four (4) general-purpose time slots may be indicated by aseries of 4-bit data values S(n)3 through S(n)0 (where “n”=the slotnumber). The status of each slot can thus assume, by way of example, oneof the 16 possible values set forth in Table 1.

TABLE 1 0 Idle/Available 1 ACK 2 Registered, Tag Accepted 3 Registered,Tag Assignment (e.g., the assigned tag is reported in T5-T0 and there isonly one tag assignment in a given cycle) 4 NACK 5 NACK, Slot notRegistered 6 Persistent Registration 7 BACKOFF (e.g., abandon thecurrent protocol session and maintain IR silence until there has been atleast 200 ms of continuous IR silence) 8 Outbound Data, Broadcast 9Outbound Data, for device in Slot ((n + 1) % 4) 10 Outbound Data, fordevice in Slot ((n + 2) % 4) 11 Outbound Data, for device in Slot ((n +3) % 4) 12 Polled inbound Long Peripheral Packet 13 Polled inbound ShortPeripheral Packet 14 Reserved by the TS Controller (e.g., the TSController is reserving this slot for possible use in the future. Thismight be done in order to ensure slot availability if the TS knows thatan outbound data transmission is about to be scheduled) 15 TBDThe “End-of-Cycle” packet data may also include a tag assignment field(T5 through T0) the significance of which will be described later.

When a peripheral finds an available time slot, as indicated by a valueof zero (0) in the S(n) field for that slot, the peripheral may transmita “Peripheral Registry Request” packet to the TS controller in the nextoccurrence of that time slot. In the event that two peripheral devicessimultaneously attempt to acquire the same slot, the TS controllershould respond negatively (e.g., with a slot status of “4” or “5” as setforth in Table 1) to the corrupted data resulting from the collisionbetween the multiple, received “Peripheral Registry Request” packets.Upon detection of such a negative response, each of the peripheraldevices that transmitted the simultaneous messages in question should beprogrammed to back off, i.e., not transmit, for a variable period oftime determined, for example, as a function of a combination of theirRegistry Number and last assigned tag number. In the event that no IRactivity is detected by a peripheral device for a period of time equalto or greater than the overall round robin protocol cycle time, theperipheral device may assume that no transactions are currently takingplace and the TS controller has entered into an idle mode, in which casethe peripheral device may simply assume ownership of slot zero andinitiate activity by issuing an asynchronous “Peripheral RegistryRequest” for slot zero. Receipt of such a request by the TS Controllershould result in the TS Controller exiting its idle state andrecommencing protocol cycling.

A “Peripheral Registry” packet may be a special case of a more generallong packet, e.g., forty-two (42) bit, packet type. Turning to FIG. 6,there is illustrated an exemplary general format for a long packet,arranged in FIG. 6 as seven 6-bit long words for ease of reference. Inthis example, bit locations 1-3 and 1-4 (e.g., P1 and P2) define thepacket type: 0 or 1 for an inbound packet (i.e., from a peripheraldevice to the TS Controller), 2 for an outbound packet (i.e., from theTS Controller to one or more peripheral devices).

The data field assignments for inbound peripheral packets (i.e., P1,P2=0) are illustrated by way of example in FIG. 8. In particular, bitlocation 2-5 (e.g., REG) indicates whether this packet should beinterpreted by the TS Controller as a “Peripheral Registry Request”packet or as a “Peripheral Data” packet. For example, if “REG”=1, thepacket may be viewed as a “Peripheral Registry Request” packet with datafield significance as illustrated in FIG. 9.

Referring to example illustrated in FIG. 9, the packet may comprise a21-bit “Peripheral Registry Number” (e.g., R0 through R20) whichidentifies the peripheral device initiating the registration request anda 6-bit Tag Value (e.g., T0 through T5) to be used to uniquely identifythe peripheral device throughout the forthcoming data exchange sessionfor the duration of the registration of the peripheral device with theTS Controller. A preference as to the 6-bit tag value may be specifiedby the peripheral device as part of the “Peripheral Registry Request”packet or it may be left to be assigned by the TS Controller. In eitherevent, the actual tag value to be used for the duration of this sessionshould be confirmed by the TS Controller and communicated back to theperipheral device as part of the “End-of-Cycle” data packet which isillustrated by way of example in FIG. 6. Finally, the “PeripheralRegistration” packet may contain a 1-bit value (e.g., PRG) which is usedto request that the registration be treated as persistent by the TSController in the manner described in greater detail hereinafter.

Upon receipt of such a “Peripheral Registration Request” packet, the TScontroller may issue a “registration accepted” status for this slot inthe next “End-of-Cycle” packet (i.e., in the S(n)3 through S(n)0 fieldpreviously described in connection with FIG. 6), including confirmationof the tag number to be used (i.e., in the T5 through T0 field). In theillustrated context it will be noted that, since only one T5-T0 Tagfield is available in the “End-of-Cycle” packet, there may be only oneregistration acceptance and tag assignment in any given cycle.

While the previous description set forth the use of a forty-two (42) bitlong packet type, it will be appreciated that it is also possible tosupport peripheral registration requests formatted as short packets(e.g., twenty-four (24) bit) if desired. In this case, an abbreviatedperipheral registry number may be used where, for example, the firstportion of the registry number, perhaps a type or category indicator,may be implied by the peripheral device's use of the short packet form.

Once a peripheral device is registered and accepted by the TSController, the peripheral device may now transmit and receive data, asillustrated in FIGS. 2-4, by means of a data packets, examples of whichare illustrated in FIG. 10. Transmission of the data packets isperformed using the assigned time slot and may include the tag number.As a general rule, the time slot remains assigned to the peripheral foronly as long as necessary to complete one contiguous data transferoperation. The registration may thus expire and the time slot beautomatically de-allocated upon the occurrence of the first protocolcycle during which the peripheral does not transmit a data packet in theassigned time slot. Provision may be made, however, for peripheralswhich require a rapid reporting rate to request persistent registration,as described in greater detail hereinafter.

The tag number provided in connection with registration of a peripheraldevice and assignment of a time slot may be used in several ways,depending upon the application. In cases where one peripheral isassigned to one time slot the tag number may optionally be embeddedwithin the data transferred and used to identify a communicationsession, e.g., each completed cycle of events in which a peripheralregisters with the TS controller, a data transfer occurs, and the timeslot allocation lapses. In this case, since each individualcommunication session may be provided with its own unique tag number,the TS Controller can use the tag number to detect abnormal situationsin the communication link. For example, under error conditions, it maybe possible for a peripheral device to believe that it still has a validsession in place while the TS Controller has in fact already cancelledthe prior registration and assignment of the time slot. In this examplecase, the TS Controller can detect the tag number in a transmission fromthe peripheral device, which tag number has been noted as being expiredby the TS Controller—as part of the deregistration process, and takesteps, e.g., issue a “NACK, slot not registered” or a “backoff” messageto the peripheral as may be seen in the “Cycle Completion” packetillustrated by way of example in FIG. 6, to cause the peripheral to stoptransmitting data and initiate a new peripheral registry request.

In other applications where multiple, identical peripheral devices arein use, for example game controllers, classroom response units, or thelike, the tag number may be used to uniquely distinguish individualperipheral devices. The tag number provided in connection with theassignment may also be useful in the case where a time slot is beingshared by several peripheral devices on a polled basis under control ofthe TS Controller. In this case, the tag number can be used by the TSController to sequence transmissions by the peripheral devices. By wayof example, each successive polled slot could have the polled tag numberincremented by 1 as described in footnote 1 to the “Cycle Completion”packet definition illustrated in FIG. 6.

Once registered and accepted, a peripheral device may transfer data tothe TS controller in its assigned time slot using one of severalpossible packet formats, examples of which are illustrated in FIG. 10.As can be seen, both long packets (e.g., FIGS. 10 a and 10 b) and shortpackets (e.g., FIG. 10 c) may be supported. The TS controller maydifferentiate between the two packet sizes by simply monitoring thenumber of bits received. Different packet layouts may also be supported,as illustrated by the two exemplary long packets illustrated in FIGS. 10a and 10 b. The packet format illustrated in FIG. 10 a may be suitable,for example, for use by general purpose human interface peripheraldevices and for the initial “Peripheral Registry Request” packet, whilethe format illustrated in FIG. 10 b may be suitable, for example, forapplications where maximum data transfer payload is required. Sincethese packets cannot be differentiated by length, provision may be madein the packet contents for a field (e.g., bits 1-3 and 1-4, or P0,P1with reference to FIG. 7) to indicate to the receiving TS Controllerwhich type the packet is being transmitted.

To maintain slot synchronization, the TS Controller may transmit markerpulses 10 to indicate the end of each assigned time slot interval, asillustrated in FIGS. 2-4. Variable timing for a time slot may beachieved by the TS Controller monitoring each assigned time slot foractivity. If no activity occurs within a specified period after thestart of an assigned time slot (that period being smaller than the timerequired to transmit a complete data packet), the TS Controller may beprogrammed to assume that the peripheral which is currently assignedthat time slot has nothing to transmit and, thereby, cause the issuanceof an end of time slot marker pulse. An example of this can be seen at40 in FIG. 4. If the transmission of data is detected, however, the TSController may be programmed to issue the marker pulse 10 only after thedata packet is completed and transmission from the peripheral ends. Itcan thus be seen that variable length data packets are also possibleusing this scheme. Similar logic may also be used in the case ofunassigned time slots, where the TS Controller first monitors for any“Peripheral Registry Request” packet transmissions before issuing an endof slot marker pulse 10.

In the case where the communications link is currently inactive, e.g.,in the case of start-up or where all time slots are empty and noregistrations are currently indicated as being active in the TSController, the TS Controller may be optionally programmed to shut downand switch to a listen only mode. In such a case, a peripheral devicethat wishes to register and which detects no transmission activity onthe communication link, may issue an asynchronous “Peripheral Registry”request packet to wake the TS Controller. In response, the TS Controllershould start the protocol cycling in the manner described previously.

As noted previously, provision may also be made to allow peripheraldevices which require a rapid reporting rate to request persistentregistration with the TS Controller. Generally, persistent registrationallows for the reduction of protocol latencies during periods ofcontinuous peripheral activity in which the reporting rate would be lowenough to require registration prior to each data report. By specifyingpersistent registration, a peripheral device can maintain its slotallocation between key repeats, rapid keying, etc.

When a peripheral device specifies persistent registration, the timeslot allocation assigned to that peripheral device may remain active fora predetermined number of empty protocol cycles, e.g., up to thirteen(13), following a protocol cycle in which a packet was successfullytransmitted in the allocated time slot. Persistent registration would beutilized, for example, when the default behavior for non-persistent slotallocation is set to cause the TS Controller to de-allocate a slotfollowing a single empty protocol cycle.

To ensure the receipt of a new packet transmitted by the peripheraldevice within the exemplary 13 protocol cycles of a previous packettransmission by that peripheral device, the peripheral device shouldlisten for a “Cycle Completion” packet and confirm that its previoustime slot is still reserved by the TS Controller under persistentregistration (e.g., as indicated by the tag value). If the TS Controllerhas persisted the registration, the peripheral device can simply sendits data packet in the appropriate time slot. Otherwise the peripheraldevice should have to re-register with the TS Controller as usual.

Similarly, whenever the peripheral device goes to sleep and looses trackof the time slot, the peripheral device should be programmed to forgetits persistent registration, i.e., the peripheral would simply have toregister with the TS Controller as usual. However, to avoid time slotexhaustion during rapid keying, a peripheral device should not go tosleep until it has been inactive long enough that its persistentregistration tag would have expired by the time it awoke from a new userevent and tried to establish a new session. To avoid time slotexhaustion during a marginal IR Link, the allocation of a time slot topersistent registration may not be actually confirmed until a datapacket is received in the allocated slot from the registeringperipheral. Reception of a data packet in this manner providesconfirmation that the peripheral successfully received the “CycleCompletion” packet granting the persistent registration of the timeslot.

When the TS controller wishes to transmit outbound data to one or moreperipheral devices, this may be accomplished by first indicating in an“End-of-Cycle” packet which slot(s) in the forthcoming protocol cyclewill contain outbound data packets from the TS controller, and whichdevice(s) they are intended for. More specifically, with reference toFIG. 6 and Table 1, four of the possible slot status S(n)0 through S(n)3values (8 through 11) may be used for this purpose and assigned thefollowing significance: 8=broadcast (i.e., intended for all devicescapable of receiving the data), 9=the device currently registered in thetime slot one ahead of this one, 10=the device currently registered inthe time slot two ahead of this one, and 11=the device currentlyregistered in the time slot three ahead of this one. For these purposes,it will be appreciated that “ahead” in this context implies a circularreference, i.e., wrapping around from the last slot to the first slot,e.g. a value of “2” in the slot three status field S(3)0 through S(3)3indicates that the outbound data will be located in slot one. FIG. 11illustrates by way of example the format of such an outbound data packetfrom the TS controller. It will be noted that the TS controller mayrequest that successful receipt of the data be acknowledged by thetarget peripheral by setting, for example, the value of bit 1-2 “AR”(e.g., acknowledgement required) to “1.” If so requested, receipt of thedata may be acknowledged by the peripheral device within the nextinbound packet from it to the TS controller using, for example, theappropriate A1, A2 or A3 bit locations shown in FIG. 8, 9 or 10 a. In asimilar manner to that described before, the A1 through A3 bits relateto the outbound transmission that was located circularly 1, 2 or 3 slotsahead of the current slot.

During polled operation, the TS controller may poll a single peripheraldevice in each protocol cycle by setting the status of a single timeslot in the “End-of Cycle” packet to “Polled Inbound” and placing theTag number of the peripheral device being polled in the tag value field.The device assigned that Tag number may then respond with a data packetin the indicated time slot of the upcoming cycle. In an alternativeembodiment which may be used when more rapid polling of multipleperipheral devices in desirable, the TS controller may set the status ofmultiple time slots to “Polled Inbound,” in which case the value in theTag number field represents the peripheral device which is to respond inthe first assigned time slot. The subsequent time slots would then beused, by implication, for responses from the next sequentially Tagnumbered peripheral devices. By way of example, if three of the fourslots had status “Polled Inbound” and the Tag value was “5,” this wouldimply that the peripheral assigned Tag “5” was to respond in the firstslot, the peripheral assigned Tag “6” was to respond in the second slot,and the peripheral assigned Tag “7” was to respond in the third slot. Asubsequent protocol cycle might then continue inbound polling from theperipheral device assigned Tag “8” and so on. In this manner, multipledevices may be polled in each protocol cycle under the supervision ofthe TS controller.

While various concepts have been described in detail, it will beappreciated by those skilled in the art that various modifications andalternatives to those concepts could be developed in light of theoverall teachings of the disclosure. For example, it should beappreciated that the concepts described herein might also be applicableto other bi-directional wireless protocols and encoding schemes and,therefore, need not be limited to IR communication protocols. As such,the particular concepts disclosed are meant to be illustrative only andnot limiting as to the scope of the invention which is to be given thefull breadth of the appended claims and any equivalents thereof.

What is claimed is:
 1. A time slot controller, comprising: a processing device; and a non-transitory, computer-readable media having stored thereon instructions executable by the processing device, the instructions facilitating communications between the time slot controller and a peripheral device via use of a wireless communications link system comprised of a plurality of communications time slots; wherein the instructions cause the time slot controller to assign to the peripheral device a unique tag number for subsequent use by the peripheral device in connection with an individual communications session with the time slot controller via use of at least one of the plurality of time slots whereupon, in response to receiving a data communication from the peripheral device in the at least one of the plurality of time slots, the instructions further cause the time slot controller to automatically determine if the unique tag number included with the data communication has been made invalid and, when the unique tag number included with the data communication has been made invalid, to automatically send to the peripheral device a communication for causing the peripheral device to stop transmitting data communications to the time slot controller in the at least one of the plurality of time slots.
 2. The time slot controller as recited in claim 1, wherein the instructions cause the time slot controller to automatically assign the unique tag number to the peripheral device in response to a registration request communication being received from the peripheral device.
 3. The time slot controller as recited in claim 2, wherein the instruction cause the time slot controller to automatically communicate the assigned tag number to the peripheral device in an end-of-cycle data packet.
 4. The time slot controller as recited in claim 1, wherein the instruction cause the time slot controller to make the unique tag number assigned to the peripheral device invalid upon an occurrence of a protocol cycle during which the peripheral device fails to transmit a data communication.
 5. The time slot controller as recited in claim 1, wherein the instruction cause the time slot controller to include the unique tag number with a data communication intended for the peripheral device transmitted in one or more of the plurality of communications time slots.
 6. A system, comprising: a peripheral device; and a time slot controller, wherein the time slot controller is adapted to assign to the peripheral device a unique tag number for subsequent use by the peripheral device in connection with an individual communications session with the time slot controller via use of at least one of a plurality of time slots in a communication system linking the peripheral device and the time slot controller whereupon, in response to receiving a data communication from the peripheral device in the at least one of the plurality of time slots, the time slot controller is caused to automatically determine if the unique tag number included with the data communication has been made invalid and, when the unique tag number included with the data communication has been made invalid, to automatically send to the peripheral device a communication for causing the peripheral device to stop transmitting data communications to the time slot controller in the at least one of the plurality of time slots.
 7. The system as recited in claim 6, wherein the time slot controller automatically assigns the unique tag number to the peripheral device in response to a registration request communication being received from the peripheral device.
 8. The system as recited in claim 7, wherein the time slot controller automatically communicates the assigned tag number to the peripheral device in an end-of-cycle data packet.
 9. The system as recited in claim 6, wherein the time slot controller makes the unique tag number assigned to the peripheral device invalid upon an occurrence of a protocol cycle during which the peripheral device fails to transmit a data communication.
 10. The system as recited in claim 6, wherein the time slot controller includes the unique tag number with a data communication intended for the peripheral device transmitted in one or more of the plurality of communications time slots.
 11. The system as recited in claim 6, wherein the peripheral device communicates a request for a preferred tag number assignment for use as the unique tag number to the time slot controller in a registration request communication.
 12. The system as recited in claim 11, wherein the time slot controller automatically communicates a confirmation of an acceptance of the preferred tag number assignment for use as the unique assigned tag number back to the peripheral device in response to the registration request communication.
 13. The system as recited in claim 12, wherein the time slot controller automatically communicates the confirmation of the assigned tag number back to the peripheral device in an end-of-cycle data packet. 